Hi,
I understand that I can add entries into DOORSHOME/lib/dxl/ in order to create custom menus that will show up in formal modules.
A couple of questions arise:
-
Is there any way to do this on a per-module basis? I.e. I want the menu entry to show up only when the user is viewing module 'abc'. Obviously the script can check the module on which it's being run, but it would be better not to display it at all.
-
Is there any way to do this server-side? Or on a shared drive? We have many local installations of the DOORS client; having to keep this updated across a range of client installations seems very cumbersome (besides, it seems wrong to muck around with the program installation directory).
SystemAdmin - Mon Apr 27 09:51:52 EDT 2009 |
|
Re: Menu entries to run DXL
SystemAdmin - Mon Apr 27 09:59:26 EDT 2009
Apologies for the many duplicate posts; the web server kept throwing messages to the effect that my postings weren't coming through.
|
|
Re: Menu entries to run DXL
Ron_Lewis - Mon Apr 27 11:43:23 EDT 2009
There is two way to create a shared drive directory of dxl scripts.
1. look in help file under command line switches.
2. look on old forum for registry setup.
|
|
Re: Menu entries to run DXL
SystemAdmin - Mon Apr 27 12:38:41 EDT 2009 Ron_Lewis - Mon Apr 27 11:43:23 EDT 2009
There is two way to create a shared drive directory of dxl scripts.
1. look in help file under command line switches.
2. look on old forum for registry setup.
@echo off
@rem #
@set TELELOGIC_LICENSE_FILE=19353@172.30.220.90
@set DOORS_HOME=\\albert\doors_client\DOORS_8.3
@set LocalData=%TEMP%
@set Security=SOFT
@rem #
@set BrowserName=C:\Program Files\Internet Explorer\IEXPLORE.EXE
@rem set oleopenlimit=5
@rem set Version=80000000
@rem #
@START %DOORS_HOME%\bin\doors.exe -home %DOORS_HOME% -data 36690@Albert -a Z:\dt\prd\SAC\Addins -J Z:\dt\prd\SAC\ProjectAddins -o READ_ONLY -O READ_ONLY
@CLS
@EXIT
|
|
Re: Menu entries to run DXL
SystemAdmin - Wed Apr 29 05:27:07 EDT 2009 SystemAdmin - Mon Apr 27 12:38:41 EDT 2009
The best way to do this is to run in batch mode - i.e. you have a single client install on the server and each user accesses that installation via a batch file. Below is an example batch file running a doors installation on a server called “albert”, which also serves the database to port 36690. Additional module and project level tools are stored on a local “Z” drive, but these could also be on a server. This gives flexibility to have company wide tools as well as user or project specific ones:-
@echo off
@rem #
@set TELELOGIC_LICENSE_FILE=19353@172.30.220.90
@set DOORS_HOME=\\albert\doors_client\DOORS_8.3
@set LocalData=%TEMP%
@set Security=SOFT
@rem #
@set BrowserName=C:\Program Files\Internet Explorer\IEXPLORE.EXE
@rem set oleopenlimit=5
@rem set Version=80000000
@rem #
@START %DOORS_HOME%\bin\doors.exe -home %DOORS_HOME% -data 36690@Albert -a Z:\dt\prd\SAC\Addins -J Z:\dt\prd\SAC\ProjectAddins -o READ_ONLY -O READ_ONLY
@CLS
@EXIT
|
|